I ran into this exact same issue. The file was in my bundle, I could see this when running my iOS app on my simulator and using Finder to inspect the app bundle. If I switched String(contentsOfFile: String) to String(contentsOf: URL) it worked. -Ed

I was searching the internet for an answer to the same question. In my Enterprise account, I go to certificates. I now see "iOS Distribution" cert and "iOS Distribution Managed" cert. Two different creators, two different expiration dates.

Check your 'Build Active Architecture Only' build settings. You probably want for everything but release configuration to be set to 'Yes'. Sounds like when you are building for your simulator, (assuming you are on intel Mac), your project is building the App for Intel and arm64 architecture. My guess is that your dependency code, (pod project build settings), has 'Build Active Architecture Only' set to 'Yes', and so is only building for Intel architecture, and hence you get the can't find module because yeah, it's not built for current architecture which is Intel when deploying to simulator.